1. SIAM started, but was apparently not publishing to SSDS

This was due to a time problem.  WHen the stack booted, it thought it was April 29, 2009.  Presumably, the data was publishing to SSDS, but to the wrong time/date.  It didn't display because the SSDS web page displays the most recent data, and the Apr 29 data wasn't "recent".

 2. GUI Problems

This was due to an incorrect setting for the SIAM_CODEBASE environment variable.   It was set to 'http://`hostname`/codebase', which resolves to http://foce/codebase; It should be http://foce.mars.mbari.org/codebase; Thus internal (executed on the node) applications could get to the SIAM classes, but external applications could not.

 3. Couldn't run the camera GUI

Pilot error.  On the FOCE laptop being operated by Chad, I (Bob) had set the address incorrectly for the Digi serial server.

4. Couldn't run motors

Pilot error again.  I forgot that the 'motor' application required a '-e' to enable the motors.

5. Failed hard disk check at startup

Same time problem as #1 above.  The time discrepancy forced the disk check which otherwise should not have been scheduled.  And presumably, the time discrepancy was caught by the disk check (files dated later than 'current'), causing an error.  I'm going to set the hardware clock and reboot to verify.

6. NTP not running

Current theory is also the time problem as above.  NTP will crap out if the time is too far off.

Edit -- I talked to Pete Braccio, and apparently nodes on MARS can't use the shore time servers.  The ntp port is blocked by the routers.  I've now changed the FOCE time server to the correct MARS time server at 10.91.128.55.